Apparatus and method for uplink control signaling in multi-transmission reception point operation for new radio, and demodulation reference signal design

ABSTRACT

Techniques discussed herein can facilitate multi-transmission reception point (multi-TRP) operation for new radio (NR). One example apparatus may be employed at a user equipment (UE), and may comprise: an interface configured to enable the UE to communicate with two or more TRPs; and a processor that is configured to generate uplink control information (UCI) for each of the TRPs, schedule single or multiple uplink channels to carry the UCI, so that the UCI is transmitted individually or in combination to the TRPs via the interface, wherein the uplink channels comprise NR physical uplink control channel (PUCCH) and/or NR physical uplink shared channel (PUSCH). Techniques discussed herein also can facilitate demodulation reference signal design for short physical uplink control channel carrying more than 2-bit UCI for new radio.

PRIORITY CLAIM

This application claims the benefit of priority to U.S. ProvisionalPatent Application Ser. No. 62/556,959 filed Sep. 11, 2017, entitled“UPLINK CONTROL SIGNALING IN MULTI-TRANSMISSION RECEPTION POINTOPERATION FOR NEW RADIO”, and Ser. No. 62/567,178 filed Oct. 2, 2017,entitled “DEMODULATION REFERENCE SIGNAL DESIGN FOR SHORT PHYSICAL UPLINKCONTROL CHANNEL WITH MORE THAN 2 BITS UPLINK CONTROL INFORMATION”, thecontent of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present disclosure generally relates to the field of wirelesscommunication, and more specifically to techniques employable inconnection with uplink control signaling for New Radio (NR), anddemodulation reference signal design for short physical uplink controlchannel (PUCCH).

BACKGROUND

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platform. Thenext generation wireless communication system, fifth generation (5G), ornew radio (NR), will provide access to information and sharing of dataanywhere, anytime by various users and applications. NR is expected tobe a unified network/system that can meet vastly different and sometimesconflicting performance dimensions and services. These diversemulti-dimensional targets for NR are driven by different services andapplications. In general, NR will evolve based on 3GPP (Third GenerationPartnership Project) LTE (Long Term Evolution)-Advanced with additionalpotential new radio access technologies (RATS) to enrich peoples' liveswith better, simpler and seamless wireless connectivity solutions. NRwill enable everything connected by wireless and deliver fast, richcontents and services.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure will be readily understood from thedetailed description given below in reference to the accompanyingdrawings which illustrate generally, by way of example, but not by wayof limitation, various features or embodiments of the presentdisclosure. The same reference numbers may be used in different drawingsto identify the same or similar elements. Numbers provided in flowcharts and processes are provided for clarity in illustrating steps oroperations, and do not necessarily indicate a particular order orsequence of the steps or operations.

FIG. 1 illustrates example architecture of a system of a network inaccordance with some embodiments.

FIG. 2 illustrates example components of a device in accordance withsome embodiments.

FIG. 3 illustrates example interfaces of baseband circuitry inaccordance with some embodiments.

FIG. 4 is an illustration of a control plane protocol stack inaccordance with some embodiments.

FIG. 5 is an illustration of a user plane protocol stack in accordancewith some embodiments.

FIG. 6 is a block diagram illustrating components, according to someembodiments, able to read instructions from a machine-readable orcomputer-readable medium and implement one or more of the embodimentsdiscussed herein.

FIG. 7 is a diagram illustrating an example of multiple transmissionreception point (multi-TRP) operation in accordance with someembodiments.

FIG. 8 illustrates an example of scheduling multiple uplink channels tocarry uplink control information (UCI) in accordance with someembodiments.

FIG. 9 illustrates another example of scheduling multiple uplinkchannels to carry UCI in accordance with some embodiments.

FIG. 10 illustrates an example of combined UCI for multiple TRPs inaccordance with some embodiments.

FIG. 11 illustrates an example of scheduling single uplink channel tocarry the combined UCI for multiple TRPs in accordance with someembodiments.

FIG. 12 illustrates an example of scheduling multiple uplink channels tocarry combined UCI for multiple TRPs in accordance with someembodiments.

FIG. 13 illustrates one example for the scheduled uplink channels inaccordance with some embodiments.

FIG. 14 illustrates another example for the scheduled uplink channels inaccordance with some embodiments.

FIG. 15 is a flowchart illustrating an example method employable at a UEto facilitate multi-TRP operation in accordance with some embodiments.

FIG. 16 is a block diagram illustrating an example of a network node forfacilitating the multi-TRP operation in accordance with someembodiments.

FIG. 17 is a diagram illustrating an example 1700 of a short NR PUCCH inaccordance with some embodiments.

FIG. 18 is a diagram illustrating an example 1800 of a long NR PUCCH inaccordance with some embodiments.

FIG. 19 is a diagram illustrating an example 1900 of a demodulationreference signal (DM-RS) pattern for a short NR PUCCH with more than 2bits UCI in accordance with some embodiments.

FIG. 20 is a flowchart illustrating an example method 2000 employable ata UE to facilitate generating a DM-RS pattern in accordance with someembodiments.

FIG. 21 is a diagram illustrating an example of frequency-first mappingof DM-RS sequence in accordance with some embodiments.

FIG. 22 is a diagram illustrating an example of time-first mapping ofDM-RS sequence in accordance with some embodiments.

FIG. 23 illustrates an example of applying orthogonal cover code (OCC)to the DM-RS REs within 1 physical resource block (PRB).

FIG. 24 illustrates an example of applying OCC to the DM-RS REs within 2PRBs.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and notlimitation, numerous specific details are set forth such as particularstructures, architectures, interfaces, techniques, etc. in order toprovide a thorough understanding of the various aspects of variousembodiments. However, it will be apparent to those skilled in the arthaving the benefit of the present disclosure that the various aspects ofthe various embodiments may be practiced in other examples that departfrom these specific details. In certain instances, descriptions ofwell-known devices, circuits, and processes are omitted so as not toobscure the description of the various embodiments with unnecessarydetail.

References to the phrases “one embodiment”, “an embodiment”, “oneexample”, “an example” and the like throughout the disclosure indicatethat the embodiment described may include a particular feature,structure, step, material or characteristic; however, every embodimentmay not necessarily include the particular feature, structure, step,material or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. For the purposes of the disclosure,the phrase “A and/or B” means (A), or (B), or (A and B).

Embodiments described herein may be implemented into a system using anysuitably configured hardware and/or software. FIG. 1 illustrates examplearchitecture of a system 100 of a network in accordance with someembodiments. The system 100 is shown to include a user equipment (UE)101 and a UE 102. The UEs 101 and 102 are illustrated as smartphones(e.g., handheld touchscreen mobile computing devices connectable to oneor more cellular networks), but may also comprise any mobile ornon-mobile computing device, such as personal data assistants (PDAs),pagers, laptop computers, desktop computers, wireless handsets, or anycomputing device including a wireless communications interface.

In some embodiments, any of the UEs 101 and 102 can comprise an Internetof Things (IoT) UE, which can comprise a network access layer designedfor low-power IoT applications utilizing short-lived UE connections. AnIoT UE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 101 and 102 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 110—the RAN 110 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 101 and 102 utilize connections 103 and104, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs 101 and 102 may further directly exchangecommunication data via a ProSe interface 105. The ProSe interface 105may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 102 is shown to be configured to access an access point (AP) 106via connection 107. The connection 107 can comprise a local wirelessconnection, such as a connection consistent with any IEEE 802.11protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®)router. In this example, the AP 106 is shown to be connected to theInternet without connecting to the core network of the wireless system(described in further detail below).

The RAN 110 can include one or more access nodes that enable theconnections 103 and 104. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), next GenerationNodeBs (gNBs), RAN nodes, and so forth, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). The RAN 110 mayinclude one or more RAN nodes for providing macrocells, e.g., macro RANnode 111, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., low power(LP) RAN node 112.

Any of the RAN nodes 111 and 112 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 101 and 102.In some embodiments, any of the RAN nodes 111 and 112 can fulfillvarious logical functions for the RAN 110 including, but not limited to,radio network controller (RNC) functions such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In accordance with some embodiments, the UEs 101 and 102 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe RAN nodes 111 and 112 over a multicarrier communication channel inaccordance various communication techniques, such as, but not limitedto, an Orthogonal Frequency-Division Multiple Access (OFDMA)communication technique (e.g., for downlink communications) or a SingleCarrier Frequency Division Multiple Access (SC-FDMA) communicationtechnique (e.g., for uplink and ProSe or sidelink communications),although the scope of the embodiments is not limited in this respect.The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 and 112 to the UEs 101 and102, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 101 and 102. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthings. It may also inform the UEs 101 and 102 about the transportformat, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 102 within a cell) may be performed at any of the RAN nodes 111 and112 based on channel quality information fed back from any of the UEs101 and 102. The downlink resource assignment information may be sent onthe PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as an enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 110 is shown to be communicatively coupled to a core network(CN) 120—via an S1 interface 113. In embodiments, the CN 120 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 113 issplit into two parts: the S1-U interface 114, which carries traffic databetween the RAN nodes 111 and 112 and the serving gateway (S-GW) 122,and the S1-mobility management entity (MME) interface 115, which is asignaling interface between the RAN nodes 111 and 112 and MMEs 121.

In this embodiment, the CN 120 comprises the MMEs 121, the S-GW 122, thePacket Data Network (PDN) Gateway (P-GW) 123, and a home subscriberserver (HSS) 124. The MMEs 121 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 121 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 124 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 120 may comprise one or several HSSs 124, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 124 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, androutes data packets between the RAN 110 and the CN 120. In addition, theS-GW 122 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 123 may terminate a SGi interface toward a PDN. The P-GW 123may route data packets between the EPC network 123 and external networkssuch as a network including the application server 130 (alternativelyreferred to as application function (AF)) via an Internet Protocol (IP)interface 125. Generally, the application server 130 may be an elementoffering applications that use IP bearer resources with the core network(e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). Inthis embodiment, the P-GW 123 is shown to be communicatively coupled toan application server 130 via an IP communications interface 125. Theapplication server 130 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 101 and 102 via the CN 120.

The P-GW 123 may further be a node for policy enforcement and chargingdata collection. Policy and Charging Enforcement Function (PCRF) 126 isthe policy and charging control element of the CN 120. In a non-roamingscenario, there may be a single PCRF in the Home Public Land MobileNetwork (HPLMN) associated with a UE's Internet Protocol ConnectivityAccess Network (IP-CAN) session. In a roaming scenario with localbreakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF126 may be communicatively coupled to the application server 130 via theP-GW 123. The application server 130 may signal the PCRF 126 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 126 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 130.

FIG. 2 illustrates example components of a device 200 in accordance withsome embodiments. In some embodiments, the device 200 may includeapplication circuitry 202, baseband circuitry 204, Radio Frequency (RF)circuitry 206, front-end module (FEM) circuitry 208, one or moreantennas 210, and power management circuitry (PMC) 212 coupled togetherat least as shown. The components of the illustrated device 200 may beincluded in a UE or a RAN node. In some embodiments, the device 200 mayinclude less elements (e.g., a RAN node may not utilize applicationcircuitry 202, and instead include a processor/controller to process IPdata received from an EPC). In some embodiments, the device 200 mayinclude additional elements such as, for example, memory/storage,display, camera, sensor, or input/output (I/O) interface. In otherembodiments, the components described below may be included in more thanone device (e.g., said circuitries may be separately included in morethan one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 202 may include one or more applicationprocessors. For example, the application circuitry 202 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 200. In some embodiments,processors of application circuitry 202 may process IP data packetsreceived from an EPC.

The baseband circuitry 204 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 204 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 206 and to generate baseband signals for atransmit signal path of the RF circuitry 206. Baseband processingcircuitry 204 may interface with the application circuitry 202 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 206. For example, in some embodiments,the baseband circuitry 204 may include a third generation (3G) basebandprocessor 204A, a fourth generation (4G) baseband processor 204B, afifth generation (5G) baseband processor 204C, or other basebandprocessor(s) 204D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g.,one or more of baseband processors 204A-D) may handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 206. In other embodiments, some or all ofthe functionality of baseband processors 204A-D may be included inmodules stored in the memory 204G and executed via a Central ProcessingUnit (CPU) 204E. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 204 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 204 may include convolution, tail-biting convolution,turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 204 may include one or moreaudio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F maybe include elements for compression/decompression and echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 204 and the application circuitry202 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 204 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 204 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 204 is configured to supportradio communications of more than one wireless protocol may be referredto as multi-mode baseband circuitry.

RF circuitry 206 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 206 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 206 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 208 and provide baseband signals to the baseband circuitry204. RF circuitry 206 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 204 and provide RF output signals to the FEMcircuitry 208 for transmission.

In some embodiments, the receive signal path of the RF circuitry 206 mayinclude mixer circuitry 206A, amplifier circuitry 206B and filtercircuitry 206C. In some embodiments, the transmit signal path of the RFcircuitry 206 may include filter circuitry 206C and mixer circuitry206A. RF circuitry 206 may also include synthesizer circuitry 206D forsynthesizing a frequency for use by the mixer circuitry 206A of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 206A of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 208 based on thesynthesized frequency provided by synthesizer circuitry 206D. Theamplifier circuitry 206B may be configured to amplify the down-convertedsignals and the filter circuitry 206C may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 204 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, mixer circuitry 206A of the receive signal path maycomprise passive mixers, although the scope of the embodiments is notlimited in this respect.

In some embodiments, the mixer circuitry 206A of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 206D togenerate RF output signals for the FEM circuitry 208. The basebandsignals may be provided by the baseband circuitry 204 and may befiltered by filter circuitry 206C.

In some embodiments, the mixer circuitry 206A of the receive signal pathand the mixer circuitry 206A of the transmit signal path may include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry206A of the receive signal path and the mixer circuitry 206A of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 206A of the receive signal path and themixer circuitry 206A may be arranged for direct downconversion anddirect upconversion, respectively. In some embodiments, the mixercircuitry 206A of the receive signal path and the mixer circuitry 206Aof the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 206 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry204 may include a digital baseband interface to communicate with the RFcircuitry 206.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 206D may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 206D may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer comprising a phase-locked loop with a frequencydivider.

The synthesizer circuitry 206D may be configured to synthesize an outputfrequency for use by the mixer circuitry 206A of the RF circuitry 206based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 206D may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 204 orthe applications processor 202 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications processor 202.

Synthesizer circuitry 206D of the RF circuitry 206 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 206D may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (f_(LO)). Insome embodiments, the RF circuitry 206 may include an IQ/polarconverter.

FEM circuitry 208 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 210, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 206 for furtherprocessing. FEM circuitry 208 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 206 for transmission by one ormore of the one or more antennas 210. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 206, solely in the FEM 208, or in both the RFcircuitry 206 and the FEM 208.

In some embodiments, the FEM circuitry 208 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include an LNA toamplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 206). The transmitsignal path of the FEM circuitry 208 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 206), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 210).

In some embodiments, the PMC 212 may manage power provided to thebaseband circuitry 204. In particular, the PMC 212 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 212 may often be included when the device 200 iscapable of being powered by a battery, for example, when the device isincluded in a UE. The PMC 212 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204.However, in other embodiments, the PMC 212 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to,application circuitry 202, RF circuitry 206, or FEM 208.

In some embodiments, the PMC 212 may control, or otherwise be part of,various power saving mechanisms of the device 200. For example, if thedevice 200 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 200 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 200 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 200 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 200may not receive data in this state, in order to receive data, it musttransition back to RRC_Connected state.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and may power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 202 and processors of thebaseband circuitry 204 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 204, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 204 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 3 illustrates example interfaces of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 204 of FIG. 2 may comprise processors 204A-204E and a memory204G utilized by said processors. Each of the processors 204A-204E mayinclude a memory interface, 304A-304E, respectively, to send/receivedata to/from the memory 204G.

The baseband circuitry 204 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 312 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 204), an application circuitryinterface 314 (e.g., an interface to send/receive data to/from theapplication circuitry 202 of FIG. 2), an RF circuitry interface 316(e.g., an interface to send/receive data to/from RF circuitry 206 ofFIG. 2), a wireless hardware connectivity interface 318 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 320 (e.g., an interface to send/receive power or controlsignals to/from the PMC 212).

FIG. 4 is an illustration of a control plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane400 is shown as a communications protocol stack between the UE 101 (oralternatively, the UE 102), the RAN node 111 (or alternatively, the RANnode 112), and the MME 121.

The PHY layer 401 may transmit or receive information used by the MAClayer 402 over one or more air interfaces. The PHY layer 401 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as the RRClayer 405. The PHY layer 401 may still further perform error detectionon the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 402 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto PHY via transport channels, de-multiplexing MAC SDUs to one or morelogical channels from transport blocks (TB) delivered from the PHY viatransport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through hybrid automatic repeatrequest (HARQ), and logical channel prioritization.

The RLC layer 403 may operate in a plurality of modes of operation,including: Transparent Mode (TM), Unacknowledged Mode (UM), andAcknowledged Mode (AM). The RLC layer 403 may execute transfer of upperlayer protocol data units (PDUs), error correction through automaticrepeat request (ARQ) for AM data transfers, and concatenation,segmentation and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 403 may also execute re-segmentation of RLC data PDUs forAM data transfers, reorder RLC data PDUs for UM and AM data transfers,detect duplicate data for UM and AM data transfers, discard RLC SDUs forUM and AM data transfers, detect protocol errors for AM data transfers,and perform RLC re-establishment.

The PDCP layer 404 may execute header compression and decompression ofIP data, maintain PDCP Sequence Numbers (SNs), perform in-sequencedelivery of upper layer PDUs at re-establishment of lower layers,eliminate duplicates of lower layer SDUs at re-establishment of lowerlayers for radio bearers mapped on RLC AM, cipher and decipher controlplane data, perform integrity protection and integrity verification ofcontrol plane data, control timer-based discard of data, and performsecurity operations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 405 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBs) related to thenon-access stratum (NAS)), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting. Said MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 101 and the RAN node 111 may utilize a Uu interface (e.g., anLTE-Uu interface) to exchange control plane data via a protocol stackcomprising the PHY layer 401, the MAC layer 402, the RLC layer 403, thePDCP layer 404, and the RRC layer 405.

The non-access stratum (NAS) protocols 406 form the highest stratum ofthe control plane between the UE 101 and the MME 121. The NAS protocols406 support the mobility of the UE 101 and the session managementprocedures to establish and maintain IP connectivity between the UE 101and the P-GW 123.

The S1 Application Protocol (S1-AP) layer 415 may support the functionsof the S1 interface and comprise Elementary Procedures (EPs). An EP is aunit of interaction between the RAN node 111 and the CN 120. The S1-APlayer services may comprise two groups: UE-associated services and nonUE-associated services. These services perform functions including, butnot limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as the SCTP/IP layer) 414 may ensure reliable delivery ofsignaling messages between the RAN node 111 and the MME 121 based, inpart, on the IP protocol, supported by the IP layer 413. The L2 layer412 and the L1 layer 411 may refer to communication links (e.g., wiredor wireless) used by the RAN node and the MME to exchange information.

The RAN node 111 and the MME 121 may utilize an S1-MME interface toexchange control plane data via a protocol stack comprising the L1 layer411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and theS1-AP layer 415.

FIG. 5 is an illustration of a user plane protocol stack in accordancewith some embodiments. In this embodiment, a user plane 500 is shown asa communications protocol stack between the UE 101 (or alternatively,the UE 102), the RAN node 111 (or alternatively, the RAN node 112), theS-GW 122, and the P-GW 123. The user plane 500 may utilize at least someof the same protocol layers as the control plane 400. For example, theUE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uuinterface) to exchange user plane data via a protocol stack comprisingthe PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer404.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer 504 may be used for carrying user data within theGPRS core network and between the radio access network and the corenetwork. The user data transported can be packets in any of IPv4, IPv6,or PPP formats, for example. The UDP and IP security (UDP/IP) layer 503may provide checksums for data integrity, port numbers for addressingdifferent functions at the source and destination, and encryption andauthentication on the selected data flows. The RAN node 111 and the S-GW122 may utilize an S1-U interface to exchange user plane data via aprotocol stack comprising the L1 layer 411, the L2 layer 412, the UDP/IPlayer 503, and the GTP-U layer 504. The S-GW 122 and the P-GW 123 mayutilize an 55/58a interface to exchange user plane data via a protocolstack comprising the L1 layer 411, the L2 layer 412, the UDP/IP layer503, and the GTP-U layer 504. As discussed above with respect to FIG. 4,NAS protocols support the mobility of the UE 101 and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe UE 101 and the P-GW 123.

FIG. 6 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 6 shows a diagrammaticrepresentation of hardware resources 600 including one or moreprocessors (or processor cores) 610, one or more memory/storage devices620, and one or more communication resources 630, each of which may becommunicatively coupled via a bus 640. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 602 may be executedto provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 600.

The processors 610 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 612 and a processor 614.

The memory/storage devices 620 may include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 620 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 630 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 604 or one or more databases 606 via anetwork 608. For example, the communication resources 630 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 650 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 610 to perform any one or more of the methodologies discussedherein. The instructions 650 may reside, completely or partially, withinat least one of the processors 610 (e.g., within the processor's cachememory), the memory/storage devices 620, or any suitable combinationthereof. Furthermore, any portion of the instructions 650 may betransferred to the hardware resources 600 from any combination of theperipheral devices 604 or the databases 606. Accordingly, the memory ofprocessors 610, the memory/storage devices 620, the peripheral devices604, and the databases 606 are examples of computer-readable andmachine-readable media.

For fifth generation (5G) or new radio (NR) system, high frequency bandcommunication has attracted significantly attention from the industry,since it may provide wider bandwidth to support an integratedcommunication system in future. Beam forming may be a criticaltechnology for implementation of the high frequency band communicationdue to the fact that gain of the beam forming may compensate the severepath loss caused by atmospheric attenuation, improve signal-to-noiseratio (SNR), and enlarge a coverage area. By aligning a transmissionbeam from a network node to a target UE, the radiated energy may befocused for higher energy efficiency, and the mutual interferencebetween the targeted UE and other UE(s) may be suppressed.

In case when a UE is equipped with multiple antenna panels or antennasubarrays, the UE may be able to transmit/receive signals to/frommultiple transmission reception point (TRP) simultaneously usingdifferent beams. This multi-TRP operation may facilitate increasing thenumber of layers for data transmission, and thereby improving thethroughput of the entire system.

FIG. 7 is a diagram illustrating an example 700 of multi-TRP operationin accordance with some embodiments. Although only two TRPs (i.e. TRP1701 and TRP2 702) are shown in this example, more than two TRPs may beinvolved in the multi-TRP operation.

In one example, the two TRPs 701 and 702 may be located in one and thesame radio access network (RAN) node, e.g. macro RAN node 111 shown inFIG. 1, which may be referred to as a base station (BS), NodeB (NB),evolved NodeB (eNB), next Generation NodeB (gNB), and so forth. Forexample, the TRPs may be two transceivers or two remote headends (RHs)located at a base station, and may be controlled or coordinated by acontroller within the base station.

In another example, the two TRPs 701 and 702 may be located in twodifferent networks nodes. For example, TRP1 701 may be part of one basestation, while TRP2 702 may be part of another base station. In thiscase, said TRP1 and TRP2 are controlled or coordinated by theirrespective base station controllers (BSCs) and/or a controller orcoordinator at a higher level. For example, the coordination between theTRPs may be performed via an ideal backhaul (e.g. optical fiber).

As shown in FIG. 7, the two TRPs 701 and 702 may simultaneously transmitdownlink (DL) signals to a UE (e.g. UE 101 of FIG. 1), or otherwisesimultaneously receive uplink (UL) signals from the UE, using differentbeams 703 and 704 respectively.

In this example, the UE 101 may be equipped with two or more antennapanels or antenna subarrays. Thus, the UE 101 may be capable ofsupporting the multi-TRP operation, by transmitting the UL signals todifferent TRPs or receiving the DL signals from different TRPssimultaneously using different beams.

Either the DL signals or the UL signals may include user data and/orcontrol signaling. The DL signals may be carried by one or more downlinkchannels, such as physical downlink shared channel (PDSCH), physicaldownlink control channel (PDCCH) and so on. The UL signals may becarried by one or more uplink channels, such as physical uplink sharedchannel (PUSCH), physical uplink control channel (PUCCH) and so on. Inan example, the PDSCH, PDCCH, PUSCH and PUCCH discussed in thedisclosure may be new radio (NR) PDSCH, NR PDCCH, NR PUSCH and NR PUCCH,respectively.

For example, the PDSCH may carry user data and/or higher-layer signalingto the UE. The PDCCH may carry information about transport format andresource allocations related to the PDSCH channel, among other things.

For multi-TRP operation in DL, multiple PDSCHs may be transmittedsimultaneously from several TRPs (e.g. TRP1 and TRP2 in FIG. 7) indifferent beam pair links (BPLs), so as to increase the number oftransmission layers and data throughput. Note that it was agreed in newradio (NR) that maximum number of supported NR PDCCHs corresponding tothe scheduled PDSCHs that a UE can be expected to receive in a singleslot is 2 on a per component carrier basis.

For example, the PUSCH may carry user data and/or uplink controlinformation (UCI) to the TRP, and the PUCCH may carry the UCI to theTRP.

According to some embodiments, the UE 101 may comprise an interfaceconfigured to enable the UE to communicate with two or more TRPs.Moreover, the UE 101 may further comprise a processor that may beconfigured to generate the UCI for each of the TRPs, schedule single ormultiple uplink channels to carry the UCI, so that the UCI istransmitted individually or in combination to the TRPs via theinterface, wherein the uplink channels may comprise NR PUCCH and/or NRPUSCH.

In an example, the interface of the UE may be the RF circuitry interface316 of FIG. 3, which may be configured to send/receive data to/from theRF circuitry 206 of FIG. 2. In an example, the processor of the UE maybe the central processing unit (CPU) 204E of FIG. 2 and FIG. 3.

The UCI may comprise one or more of scheduling request (SR), hybridautomatic repeat request (HARQ) acknowledgement/negative acknowledgement(ACK/NACK) feedback, channel state information (CSI) report (e.g.,channel quality indicator (CQI)), pre-coding matrix indicator (PMI), CSIresource indicator (CRI), rank indicator (RI), beam related information(e.g., layer 1-reference signal received power (L1-RSRP)), and so on.

According to some embodiments, the UCI to be carried by the NR PUSCH orNR PUCCH may comprise the HARQ ACK/NACK feedback and/or the CSI report.In an example, the PUCCH may carry the HARQACK/NACK feedback forrespective PDSCH(s) received from the TRP(s), while the PUSCH may carrythe CQI report(s) to the TRP(s).

FIG. 8 illustrates an example 800 of scheduling multiple uplink channelsto carry UCI in accordance with some embodiments. In this example 800,the UE (e.g. UE 101) may simultaneously receive two DL signals from twoTRPs, e.g. PDSCH_1 (or PDCCH_1) from the first TRP and PDSCH_2 (orPDCCH_2) from the second TRP. Accordingly, two PUCCHs are scheduled bythe UE to separately carry the UCI for the first TRP and the UCI for thesecond TRP, and these PUCCHs are multiplexed in a time divisionmultiplexing (TDM) manner, for example by occupying different symbols inthe same slot, e.g. the second to last symbol and the last symbol asshown in FIG. 8.

As a specific example, the PUCCH_1 may carry the HARQ ACK/NACK feedbackfor the corresponding PDSCH_1 (from the first TRP) to the first TRP,while the PUCCH_2 may carry the HARQ ACK/NACK feedback for thecorresponding PDSCH_2 (from the second TRP) to the second TRP.Alternatively, PUCCH_1 may carry the HARQ ACK/NACK feedback to the firstTRP, while the PUCCH_2 may carry the CSI report to the second TRP.

It should be noted that any of the above discussed PUCCHs may bereplaced with a PUSCH. It also should be noted that, although thisexample of FIG. 8 only shows the two PUCCHs, the UE may schedule morethan two uplink channels, for example, two PUCCHs and one PUSCH, asdescribed in details later with reference to FIG. 13 and FIG. 14.Moreover, the number of the TRPs is not limited to two.

Moreover, the processor (e.g. the CPU 204E) of the UE 101 may schedulethe multiple uplink channels according to resource allocation in timedomain, which may be configured by higher layers and/or dynamicallyconfigured by downlink control information (DCI) from the TRPs.

In an example, information regarding the resource allocation in timedomain may be exchanged between the TRPs in a semi-static or dynamicmanner, in order to implement coordination between the TRPs. Saidinformation may comprise one or more of frame index, slot index, symbolindex, starting symbol index and so on.

As one example, in case when there is certain coordination betweendifferent TRPs, the PUCCH and/or PUSCH carrying CSI reports for thedifferent TRPs may be multiplexed in the TDM manner. This would allowthe UE with single Tx beam or antenna port to transmit only one of PUCCHand/or PUSCH at a given time instance.

As another example, said information may indicate the position fortransmission of each PUCCH carrying the HARQ ACK/NACK feedback for eachcorresponding PDSCH. For example, in case of short PUCCH with 1-symbolduration being used for transmission of the HARQACK/NACK feedback,different symbol index for each PUCCH may be configured by higher layersand/or dynamically indicated in the DCI from different TRPs.

FIG. 9 illustrates another example 900 of scheduling multiple uplinkchannels to carry UCI in accordance with some embodiments. This example900 is similar to the example 800 in FIG. 8, except that the two PUCCHs(i.e. PUCCH_1 and PUCCH_2) are multiplexed in a frequency divisionmultiplexing (FDM) manner, e.g. occupying different frequency bands inone symbol.

Moreover, the processor (e.g. the CPU 204E) of the UE 101 may schedulethe multiple uplink channels according to resource allocation infrequency domain, which may be configured by higher layers and/ordynamically configured by the DCI from the TRPs. Said resourceallocation in frequency domain may be indicated by index of resourceelement (RE) or index of subcarrier, among others.

In an example, the resource allocation in frequency domain may becontiguous, based on semi-static or dynamic coordination betweenmultiple TRPs. For example, as shown in FIG. 9, the PUCCH_1 and thePUCCH_2 may occupy two contiguous subcarriers, or in other words, somecontiguous REs. Without the coordination between the TRPs, two PUCCHsmultiplexed in the FDM manner may be mapped on some discontiguous REs,which may not be desirable due to increased inter-modulation distortion(IMD).

In case of the UE supporting only one transmit (Tx) beam or antennaport, transmission of two PUCCHs using two Tx beams simultaneously maynot be feasible. The processor of the UE may select one of the twoPUCCHs for transmission and drop the others, based on a dropping rule orpriority rule, which may be predefined in 3GPP specification orconfigured by higher layers via NR minimum system information (MSI), NRremaining minimum system information (RMSI), NR other system information(OSI) or radio resource control (RRC) signaling. Alternatively, the UEmay drop the PUCCH according to the channel quality of different BPL.For instance, the UE may transmit the PUCCH on the BPL with betterchannel condition and drop other PUCCHs. In an example, the UE may dropthe PUCCH depending on specific implementation of the UE.

For carrier frequency below 6 GHz or above 6 GHz, if the UE employsomni-Tx beam for transmission of the PUCCHs and there is certaincoordination between the multiple TRPs, the different TRPs may allocatethe contiguous resources for the PUCCHs in the FDM manner. In this case,the UE may still be able to transmit multiple PUCCHs for a given timeinstance.

FIG. 10 illustrates an example 1000 of combined UCI for multiple TRPs inaccordance with some embodiments. As mentioned before, a UE may comprisean interface (e.g. the RF circuitry interface 316 of FIG. 3 beingconfigured to send/receive data to/from the RF circuitry 206 of FIG. 2)to enable the UE to communicate with multiple TRPs. In this case, theprocessor (e.g. the CPU 204E) of the UE (e.g. UE 101) may generateindividual UCI for each of the multiple TRPs, and then combine the UCIgenerated for each TRP into the combined UCI.

In accordance with some embodiments, the combined UCI may be encoded ina form of bit set, wherein each individual UCI for one of the TRPs maycorrespond to a subset of said bit set. For example, the UCI generatedfor the TRP1 may be encoded as the first subset having N1 bits, and theUCI generated for the TRP2 may be encoded as the second subset having N2bits, wherein both N1 and N2 are positive integer (e.g., 1, 2, . . . ).In other embodiments, the combined UCI may be encoded into other datastructure than that shown in FIG. 10.

It should be noted that, a number of bits in each subset (such as N1,N2) may be configured by higher layers and/or indicated by downlinkcontrol information (DCI) from the TRPs.

In some embodiments, the UE may combine HARQ ACK/NACK feedback for thecorresponding PDSCHs from different TRPs and transmit the combined HARQACK/NACK feedback on a PUCCH. In one example, if single codeword is usedfor each PDSCH, 1-bit HARQ ACK/NACK feedback may be fed back for eachPDSCH. It means that N1=1 and N2=1, and the total number of bits (i.e.N1+N2) for the combined HARQ ACK/NACK feedback is 2, in case of twoTRPs. In another example, if two codewords are used for each PDSCH,2-bit HARQACK/NACK feedback may be fed back for each PDSCH, which meansthat N1=2 and N2=2, and the total number of bits (i.e. N1+N2) for thecombined feedback is 4 in case of two TRPs. In yet another example, iftransmission is based on code block group (CBG), the specific values ofN1 and N2 may be configured by higher layers.

In some embodiments, the UE may combine the CSI reports for differentTRPs, and transmit the combined CSI report on a PUSCH or a PUCCH.

In some embodiments, TRP index for said bit set is predefined in 3GPPtechnical specification or configured by higher layers, e.g. via RRCsignaling.

In some embodiments, resource index may be explicitly signaled in theDCI for downlink assignment, in order to indicate the resourceallocation for PUCCH transmission for HARQ ACK/NACK feedback andaperiodic CSI report. In case of discontinuous transmission (DTX), nomatter whether the downlink assignment for data channel for a TRP hasbeen decoded correctly or not, the UE may reserve a fixed number of bitsfor a combined HARQACK/NACK feedback with a pre-defined value, e.g. allzeros. As a result, the gNB may readily identify the payload size of thePUCCH. The TRP index (or indexes) where ACK/NACK for the PDSCH may bereported can be dynamically indicated by the DCI. Alternatively, the UEmay only feedback the HARQ-ACK for the configured TRP where the downlinkassignment has been decoded correctly. Moreover, said bit set may onlyinclude the UCI bits intended for the TRPs for which the correspondingHARQ-ACK feedback is generated. In this case, the gNB may use blinddetection to detect possible payload size of the PUCCH.

FIG. 11 illustrates an example 1100 of scheduling single uplink channelto carry the combined UCI for multiple TRPs in accordance with someembodiments. After having generated the combined UCI (e.g. the bit setof FIG. 10), the processor (e.g. the CPU 204E) of the UE (e.g. UE 101)may schedule the single uplink channel, e.g. one PUCCH as shown in FIG.11, to carry the combined UCI. With the aid of the RF circuitryinterface 316 of FIG. 3 and the RF circuitry 206 of FIG. 2, the UE 101may transmit the combined UCI over the scheduled PUCCH to the TRPs.

As one example (e.g. as shown in FIG. 11), the combined UCI may betransmitted over the scheduled PUCCH simultaneously to each of the TRPs,for example, to both TRP1 701 and TRP2 702, if the UE 101 supportsmultiple transmit (Tx) beams or antenna ports (APs) for UL transmission.

As another example, the combined UCI may be transmitted over thescheduled PUCCH to one of the TRPs (e.g. TRP1 701) which may thenforward the combined UCI to the remaining TRPs (e.g. TRP2 702). Theforwarding operation may be performed with the aid of some tightcoordination between the multiple TRPs, e.g., via ideal backhaul.

For example, the UE may transmit a combined HARQ ACK/NACK feedback forthe corresponding PDSCHs (e.g. PDSCH_1 and PDSCH_2) from multiple TRPsover one PUCCH. In case of the UE supporting only one Tx beam or antennaport, the UE may perform beam sweeping on the PUCCH carrying thecombined HARQ ACK/NACK feedback to the multiple TRPs.

For example, the UE may transmit a combined CSI report to all of theTRPs. If the UE supports only one Tx beam or antenna port, the UE mayperform beam sweeping for the transmission of the combined CSI report ona PUCCH or a PUSCH.

FIG. 12 illustrates an example 1200 of scheduling multiple uplinkchannels to carry combined UCI for multiple TRPs in accordance with someembodiments. After having generated the combined UCI (e.g. the bit setof FIG. 10), the processor (e.g. the CPU 204E) of the UE (e.g. UE 101)may schedule more than one uplink channels, e.g. PUCCH_1 and PUCCH_2each carrying the combined UCI, as shown in FIG. 12.

As one example, the combined UCI may be transmitted over the two PUCCHs(e.g. PUCCH_1 and PUCCH_2) to the two TRPs (e.g. TRP1 701 and TRP2 702),if the UE 101 supports multiple transmit (Tx) beams or antenna ports(APs) for UL transmission. Moreover, the two PUCCHs may be multiplexedin the TDM or FDM manner in case of the UE supporting two Tx beams orAPs.

As another example, the combined UCI may be transmitted to each of theTRPs by means of beam sweeping if the UE supports only one Tx beam orantenna port.

In an example, the payload size of the combined UCI (e.g. the combinedHARQACK/NACK feedback) can be large. In case of scheduling a PUCCH tocarry said combined UCI, the processor of the UE 101 may be configuredto dynamically select a format of the PUCCH according to the payloadsize, or in other words, the total number of bits in said bit set ofFIG. 10.

In an example, the dynamical selection of the PUCCH is based on downlinkcontrol information (DCI) from the TRPs. Moreover, a field in the DCImay be used to indicate the resource for PUCCH transmission from a setof resource for the new PUCCH formats configured by higher layers.

For example, the technical specification 3GPP TS 38.211 version 15.2.0Release 15 (“Physical channels and modulation”) has defined the newradio (NR) PUCCH formats in the table 6.3.2.1-1 as below:

TABLE 6.3.2.1-1 PUCCH formats. Length in OFDM symbols PUCCH formatN^(PUCCH) _(symb) Number of bits 0 1-2  ≤2 1 4-14 ≤2 2 1-2  >2 3 4-14 >24 4-14 >2where N_(symb) ^(PUCCH) is the length of the PUCCH transmission in OFDMsymbols.

FIG. 13 and FIG. 14 illustrate two examples 1300 and 1400 for thescheduled uplink channels in accordance with some embodiments. In theexample 1300, the scheduled uplink channels may include one PUSCH andtwo short PUCCHs. In the example 1400, the scheduled uplink channels mayinclude one PUSCH, one long PUCCH and one short PUCCH. In otherexamples, the scheduled uplink channels may include more or less uplinkchannels than those in the example 1300 or 1400, for example, schedulingone PUSCH plus one PUCCH, or scheduling two short PUCCHs only.

In some embodiments, the term “short PUCCH” may refer to the PUCCHhaving format 2 in the above table 6.3.2.1-1. In other embodiments, theterm “short PUCCH” may refer to the PUCCH having format 0 in the abovetable 6.3.2.1-1.

In some embodiments, said long PUCCH may be the PUCCH having format 1,format 3 or format 4.

FIG. 15 is a flowchart illustrating an example method 1500 employable ata UE to facilitate multi-TRP operation in accordance with someembodiments.

In accordance with some embodiments, a machine readable medium may storeinstructions associated with the method 1500 that, when executed, maycause a UE to perform the steps of the method 1500.

At step 1502, the UE may generate uplink control information (UCI) foreach of two or more TRPs communicating with the UE.

At step 1506, the UE may schedule single or multiple uplink channels tocarry the UCI, so that the UCI may be transmitted over the scheduleduplink channels individually or in combination to the TRPs, via aninterface (e.g., the RF circuitry interface 316 of FIG. 3 tosend/receive data to/from RF circuitry 206 of FIG. 2), wherein theuplink channels may comprise new radio (NR) physical uplink controlchannel (PUCCH) and/or NR physical uplink shared channel (PUSCH).

In an embodiment, the UCI generated at step 1502 may comprise hybridautomatic repeat request (HARQ) acknowledgement/negative acknowledgement(ACK/NACK) feedback and/or channel state information (CSI) report.

In an embodiment, at step 1506, the UE may schedule the multiple uplinkchannels each carrying the UCI generated for one of the TRPs, whereinthe multiple uplink channels may be multiplexed in a time divisionmultiplexing (TDM) manner, or in a frequency division multiplexing (FDM)manner.

In an embodiment, at step 1506, the UE may schedule the multiple uplinkchannels according to resource allocation in time domain or in frequencydomain, which may be configured by higher layers and/or dynamicallyconfigured by downlink control information (DCI) from the TRPs.

As an example, the information regarding the resource allocation in timedomain may be exchanged between the TRPs in a semi-static or dynamicmanner. As another example, the resource allocation in frequency domainmay be contiguous, based on semi-static or dynamic coordination betweenthe TRPs.

In an embodiment, if the scheduled uplink channels are multiplexed inthe FDM manner, the method 1500 may comprise a further step 1508, atwhich the UE may select one of the multiple uplink channels fortransmission and drop the others, in case of the UE supporting only onetransmit (Tx) beam or antenna port.

As an example, the dropping may be based on a dropping rule or priorityrule, which may be predefined in 3GPP specification or configured byhigher layers. As another example, the dropping may be based on channelquality of the uplink channels.

In an embodiment, the method 1500 may comprise an optional step 1504after step 1502 and before step 1506. At step 1504, the UE may combinethe UCI generated for each of the TRPs into a bit set, wherein each UCIcorresponds to a subset of said bit set. In an example, a number of bitsin each subset may be configured by higher layers and/or indicated bydownlink control information (DCI) from the TRPs. And then, at step1506, the UE may schedule the single uplink channel to carry said bitset.

In an example, said bit set may be transmitted to one of the TRPs whichmay forward said bit set to the remaining TRPs. In another example, saidbit set may be transmitted simultaneously to each of the TRPs in case ofthe UE supporting multiple transmit (Tx) beams.

In an embodiment, after having combined the UCI generated for each ofthe TRPs into the bit set at step 1504, the UE may schedule the multipleuplink channels each carrying said bit set at step 1506. According tothe scheduling, said bit set may be transmitted simultaneously to eachof the TRPs if the UE supports multiple transmit (Tx) beams, or said bitset may be transmitted to each of the TRPs by means of beam sweeping ifthe UE only supports single Tx beam.

In an embodiment, TRP index for said bit set may be predefined in 3GPPtechnical specification or configured by higher layers.

In an embodiment, said bit set may only include the UCI generated forthe TRPs for the corresponding HARQ-ACK feedback.

In an embodiment, in case of scheduling a PUCCH to carry said bit set,the method 1500 may further comprise an optional step of dynamicallyselecting a format of the PUCCH based on downlink control information(DCI) from the TRPs, according to a number of bits in said bit set.

FIG. 16 is a block diagram illustrating an example of a network node forfacilitating the multi-TRP operation in accordance with someembodiments.

In an embodiment, the network node 1602 may have two or more TRPs (e.g.TRP1, TRP2, . . . TRPN). At least two of the TRPs or all of the TRPs inthe network node 1602, together with a UE, may implement the variousembodiments of multi-TRP operation, as discussed with reference to anyof FIGS. 7 to 15.

In an embodiment, the network node 1602 may comprise a processor 1604which may be configured to: enable the two or more TRPs to communicatewith a UE and to receive a bit set via single or multiple uplinkchannels, said bit set including multiple subsets each corresponding touplink control information (UCI) for one of the TRPs; coordinate betweenthe two or more TRPs; and generate downlink control information (DCI)for the UE, wherein the uplink channels may comprise NR PUCCH and/or NRPUSCH.

In an embodiment, said DCI may comprise one or more of the followings:

-   -   information indicating resource allocation in time domain for        the uplink channels;    -   information indicating resource allocation in frequency domain        for the uplink channels;    -   information indicating a number of bits in each of the multiple        subsets; and    -   information indicating a format of the PUCCH carrying the bit        set.

In accordance with some embodiments, the network node may be radioaccess network (RAN) node, e.g. macro RAN node 111 shown in FIG. 1,which may also be referred to as a base station (BS), NodeB (NB),evolved NodeB (eNB), next Generation NodeB (gNB), and so forth.

In the example 1600, the TRPs may be several transceivers or remoteheadends (RHs) located at a base station, and may be coordinated by theprocessor 1604. The processor 1604 may act as a central coordinator,which may communicate with each of the TRPs to coordinate betweendifferent TRPs.

In another example, the TRPs may be located in several differentnetworks nodes. For example, TRP1 may be part of one base station, whileTRP2 may be part of another base station. In this case, said TRP1 andTRP2 are controlled or coordinated by their respective base stationcontrollers (BSCs) and/or a controller or coordinator at a higher level.For example, the coordination between the TRPs may be performed via anideal backhaul (e.g. optical fiber).

For fifth generation (5G) or new radio (NR) communication system,various formats have been defined for physical uplink control channel(PUCCH) to meet the diverse requirements for different types of traffic.For example, the technical specification 3GPP TS 38.211 version 15.2.0Release 15 has defined the new radio (NR) PUCCH formats in the table6.3.2.1-1 as mentioned above.

FIG. 17 is a diagram illustrating an example 1700 of a short NR PUCCH inaccordance with some embodiments. The short NR PUCCH may have arelatively short duration within an uplink (UL) slot. For example, theshort NR PUCCH may have format 0 or format 2 with the duration of one ortwo OFDM symbols, as defined in the aforesaid table 6.3.2.1-1.

In the example 1700, the short NR PUCCH and a NR physical uplink sharedchannel (NR PUSCH) may be multiplexed in a time division multiplexing(TDM) manner, which can be targeted for some applications withlow-latency requirement.

In another example, two short NR PUCCHs and one NR PUSCH may bemultiplexed in the TDM manner.

Moreover, in order to accommodate the time for switching from downlink(DL) to uplink (UL) and from UL to DL and round-trip propagation delay,a guard period (GP) may be inserted between a NR physical downlinkcontrol channel (NR PDCCH) and the NR PUSCH.

FIG. 18 is a diagram illustrating an example 1800 of a long NR PUCCH inaccordance with some embodiments. The long NR PUCCH may have arelatively long duration within the UL slot. For example, the long NRPUCCH may have format 1, format 3 or format 4 with the duration of 4-14OFDM symbols (i.e. spanning any number of symbols from 4 to 14 within aslot), as defined in the aforesaid table 6.3.2.1-1.

In the example 1800, the long NR PUCCH and a NR PUSCH may be multiplexedin a frequency division multiplexing (FDM) manner. Moreover, more OFDMsymbols than those used for the short NR PUCCH can be allocated for thelong NR PUCCH, in order to improve link budget and uplink coverage forcontrol channel.

Similarly, in view of the switching time and the round-trip propagationdelay, the GP may be inserted between the NR PDCCH and the NR PUCCH, NRPUSCH.

In accordance with some embodiments, the short NR PUCCH and the long NRPUCCH may carry uplink control information (UCI). The UCI may compriseone or more of scheduling request (SR), hybrid automatic repeat request(HARQ) acknowledgement/negative acknowledgement (ACK/NACK) feedback,channel state information (CSI) report (e.g., channel quality indicator(CQI)), pre-coding matrix indicator (PMI), CSI resource indicator (CRI),rank indicator (RI), beam related information (e.g., layer 1-referencesignal received power (L1-RSRP)), and so on.

In an example, for a given UE (e.g. UE 101 or UE 102), one short NRPUCCH and one long NR PUCCH can be multiplexed in the TDM manner in thesame slot (e.g. as shown in FIG. 14). They may be used for differenttypes of traffic having different requirements. For example, the shortPUCCH may carry the HARQ ACK/NACK feedback being time-critical, whilethe long PUCCH may carry the CSI report having a relatively largepayload size.

In accordance with some embodiments, demodulation reference signal(DM-RS) generated by a UE may be used by a network node (e.g. gNB, orTRP) for channel estimation, coherent demodulation of the received dataand so on. Use of a properly designed DM-RS may substantially enhancethe performance of a wireless communication system. Embodimentsdescribed hereinafter may be directed to detailed DM-RS design for ashort NR PUCCH with more than 2 bits UCI.

FIG. 19 is a diagram illustrating an example 1900 of a DM-RS pattern fora short NR PUCCH with more than 2 bits UCI in accordance with someembodiments. For example, the short NR PUCCH with more than 2 bits UCImay refer to the NR PUCCH having format 2 in the aforesaid table6.3.2.1-1. Moreover, one short NR PUCCH may span one or two symbols.

As shown in the example 1900, the short NR PUCCH may span one symbolcorresponding to one resource block (RB). A given RB may have 12resource elements (REs), wherein an index of a RE may be an integerranging from 0 to 11, i.e. RE₀, RE₁ . . . RE₁₁. For this short NR PUCCHcarrying more than 2 bits UCI, the DM-RS and the UCI may be multiplexedon the NR PUCCH in the FDM manner. As an example, the DM-RS may bemapped on four REs (e.g. RE₁, RE₄, RE₇, RE₁₀), while the UCI may bemapped on any of the remaining REs.

In accordance with some embodiments, a pseudo noise (PN) sequence may beused to generate the DM-RS.

In an example, the PN sequence as used for PUSCH may be used for DM-RSfor the short NR PUCCH with more than 2 bits UCI.

FIG. 20 is a flowchart illustrating an example method 2000 employable ata UE to facilitate generating a DM-RS pattern in accordance with someembodiments. The method may be accomplished by the UE 101 or the UE 102in FIG. 1, in particular, by one or more processors (e.g. the CPU 204Eof FIG. 2 or FIG. 3), and optionally the memory 204G of FIG. 2 or FIG.3.

At step 2004, the UE may generate a PN sequence based on aninitialization seed. At step 2006, the UE may generate a DM-RS sequencebased on the PN sequence generated at step 2004. And then, at step 2008,the UE may map the DM-RS sequence on physical resource allocated fortransmission of a short NR PUCCH with more than 2 bits UCI.

In accordance with some embodiments, the method 2000 may furthercomprise a step 2002 of defining an initialization seed as a function ofone or more of the following parameters:

-   -   slot index or mini-slot index for transmission of the short NR        PUCCH;    -   symbol index or starting symbol index for transmission of the        short NR PUCCH;    -   scrambling identity (ID), or physical cell ID when the        scrambling ID is not available;    -   beam ID; and    -   UE-specific parameter.

The UE-specific parameter may include, but not be limited to, abandwidth part (BWP) ID, an offset parameter, or a UE ID including acell radio network temporary identifier (C-RNTI) of the UE.

As one example, the scrambling ID may be configured by higher layers viaNR minimum system information (MSI), NR remaining minimum systeminformation (RMSI), NR other system information (OSI), radio resourcecontrol (RRC) signaling, or the like.

As another example, the scrambling ID may be dynamically indicated bydownlink control information (DCI) from a network node (e.g. gNB orTRP).

As still another example, in uplink power control, there can be multiplesets of {P0, alpha}, depending on traffic types or beam pair links orwaveforms. The scrambling ID may be configured based on an index of aset of {P0, alpha} for uplink power control and/or pathloss.

Moreover, the scrambling ID may be configured independently fordifferent bandwidth parts (BWPs) being configured or being active withina system bandwidth. Alternatively or in addition, the scrambling ID maybe configured independently for different types of the UCI. For example,the scrambling ID with a value of 0 may be selected for the HARQACK/NACK feedback, while the scrambling ID with a value of 1 may beselected for the CSI report.

If the UCI carried by the short NR PUCCH is the HARQ ACK/NACK feedbackfor a corresponding PDSCH from a network node, the scrambling ID usedfor transmission of the DM-RS sequence on the short NR PUCCH may be thesame as that for transmission of the DM-RS sequence on the PDSCH.Alternatively, the scrambling ID may be dynamically switched accordingto the DCI from the network node. For example, a 1-bit indicator in theDCI may be used to dynamically switch between two configured scramblingIDs.

If the UCI carried by the short NR PUCCH is a CSI report, the scramblingID used for transmission of the DM-RS sequence on the short NR PUCCH maybe configured by higher layers via UE-specific RRC signaling. In casewhen the configured value is not available, the scrambling ID may beequal to a physical cell ID.

In some embodiments, the initialization seed may be defined at step 2002in accordance with the following function:

c _(init)=(14·(n _(s)+1)+l+1)·(2·n _(ID,m) ^(PUCCH)+1)·c ₀ +c ₁

where:

c₀, c₁ are constants, e.g., c₀=2¹⁶ and c₁=2, which may be predefined inthe 3GPP technical specification;

n_(s) is the slot index for transmission of the short NR PUCCH;

-   -   l is the symbol index or starting symbol index for transmission        of the short NR PUCCH; and

n_(ID,m) ^(PUCCH) is the m^(th) scrambling ID for transmission of theshort NR PUCCH.

It is to be noted that m may be configured by higher layers ordynamically indicated in the DCI for scheduling of PDSCH, or acombination thereof. In an example, n_(ID,m) ^(PUCCH)=0 or n_(ID,m)^(PUCCH)=1, which may be configured by higher layers.

In another example, when the value of n_(ID,m) ^(PUCCH) is notconfigured by higher layers, n_(ID,m) ^(PUCCH)=n_(ID) ^(cell) (i.e. cellID), or n_(ID,m) ^(PUCCH)=f(n_(ID) ^(cell),m) wherein the function f( )may be predefined in the technical specification.

In case of the short NR PUCCH spanning two symbols, the PN sequence fortransmission of DM-RS on the short NR PUCCH may be independentlygenerated for each symbol, e.g., by mean of including a symbol index “l”as a variable in the process for generating the PN sequence. As anexample, the initialization seed may be defined independently for eachsymbol based on its respective symbol index. Accordingly, the abovefunction for generating initialization seed may be rewritten as:

c _(init)(l)=(14·(n _(s)+1)+l+1)·(2·n _(ID,m) ^(PUCCH)+1)·c ₀ +c ₁

In some embodiments, the initialization seed may be defined at step 2002in accordance with the following function:

c _(init)=(14·(n _(s)+1)+l+1)·(2·n _(ID) ^(n) ^(SCID) +1)·c ₀ +n _(ID)^(n) ^(SCID)

where:

c₀ is constant, e.g., c₀=2¹⁶, which may be predefined in the 3GPPtechnical specification;

n_(s) is the slot index for transmission of the short NR PUCCH;

l is the symbol index or starting symbol index for transmission of theshort NR PUCCH; and

n_(ID) ^(n) ^(SCID) may be configured by higher layers or dynamicallyindicated in the DCI for scheduling of PDSCH, for example, n_(ID) ^(n)^(SCID) =0 or 1.

In some embodiments, the initialization seed may be defined at step 2002in accordance with the following function:

c _(init)=(n _(s)+1)·(2·n _(ID,m) ^(PUCCH)+1)·c ₀ +n _(RNTI)

where:

c₀ is constant, e.g., c₀=2¹⁶, which may be predefined in the 3GPPtechnical specification;

n_(s) is the slot index for transmission of the short NR PUCCH;

n_(ID,m) ^(PUCCH) is the m^(th) scrambling ID for transmission of theshort NR PUCCH; and

n_(RNTI) is the C-RNTI for a given UE, which may be referred to astemporary C-RNTI (TC-RNTI) before the UE obtains a C-RNTI, in case ofthe short NR PUCCH carrying HARQ-ACK/NACK feedback for Msg. 4transmission in random access channel (RACH) procedure.

After having defined the initialization seed according to any of theabove embodiments or obtained the initialization seed by otherapproaches (e.g. directly retrieving an initialization seed from amemory or storage device), the UE may initialize a PN sequence generatorwith the initialization seed to generate the PN sequence (at step 2004).

In an example, the UE may generate the same PN sequence for the DM-RSsequence on the short NR PUCCH and on a PUSCH with cyclicprefix-orthogonal frequency division multiplexing (CP-OFDM) basedwaveform.

After then, the UE may generate a DM-RS sequence based on the generatedPN sequence at step 2006, and then, map the DM-RS sequence on physicalresource allocated for transmission of the short NR PUCCH with more than2 bits UCI at step 2008.

Various embodiments of physical resource mapping for the short NR PUCCHwith more than 2 bits UCI are provided as below.

In one embodiment, the UE may generate the DM-RS sequence according toat least a maximum number of physical resource blocks (PRBs) supportedfor a given subcarrier spacing within a wideband component carrier (CC).For example, if the wideband CC occupies a bandwidth of 100 MHz and thegiven subcarrier spacing is 15 KHz, then the maximum number of PRBs maybe about 275. As such, the UE may map the DM-RS sequence on the physicalresource allocated for transmission of the short NR PUCCH with more than2 bits UCI, using a common PRB indexing (i.e. from 0 to 274) with regardto the wideband CC.

In an example, the given subcarrier spacing A f may have other valuedepending on μ, according to the table as below:

μ Δf = 2^(μ) · 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60Normal, Extended 3 120 Normal 4 240 Normal

In another embodiment, the UE may generate the DM-RS sequence accordingto at least a total number of PRBs supported for a given subcarrierspacing within a configured bandwidth part (BWP), for example 10 MHz or20 MHz. As such, the UE may map the DM-RS sequence on the physicalresource allocated for transmission of the short NR PUCCH with more than2 bits UCI, using a UE-specific PRB indexing for the given subcarrierspacing within the configured BWP.

In still another embodiment, the UE may generate the DM-RS sequenceaccording to at least a number of PRBs allocated in frequency domain fortransmission of the short PUCCH with more than 2 bits UCI, and directlymap the DM-RS sequence on the allocated PRBs.

In case of the short NR PUCCH spanning 2 symbols, the DM-RS sequence maybe generated according to (i) any of said maximum number of PRBs withinthe wideband CC, said total number of PRBs within the configured BWP andsaid number of allocated PRBs, and additionally according to (ii) anumber of symbols (i.e. “2” in this case) allocated in time domain fortransmission of the short NR PUCCH. After the modulation, the DM-RSsequence may be mapped on the DM-RS REs in allocated resource for eachsymbol of the short NR PUCCH transmission.

FIG. 21 is a diagram illustrating an example of frequency-first mappingof DM-RS sequence in accordance with some embodiments. FIG. 22 is adiagram illustrating an example of time-first mapping of DM-RS sequencein accordance with some embodiments. In these examples, localizedresource is allocated for the short NR PUCCH.

In case of the short NR PUCCH spanning one symbol, the DM-RS sequencemay be mapped on the DM-RS REs in the allocated resource fortransmission of the short NR PUCCH, in the frequency-first mappingmanner, i.e. being mapped on the DM-RS REs for this symbol in thefrequency ascending or descending order.

In case of the short NR PUCCH spanning two symbols, either time-firstmapping or frequency-first mapping can be employed to map the DM-RSsequence on the DM-RS REs in the allocated resource for transmission ofthe short NR PUCCH.

In an example, whether to select the time-first mapping manner orfrequency-first mapping manner may be configured by higher layers, viaNR minimum system information (MSI), NR remaining minimum systeminformation (RMSI), NR other system information (OSI), radio resourcecontrol (RRC) signaling or the like.

When employing the frequency-first mapping of FIG. 21, the DM-RSsequence may be firstly mapped on the DM-RS REs for the first symbol inthe frequency ascending or descending order, and then be mapped on theDM-RS REs for the second symbol in a frequency ascending or descendingorder only after all of the DM-RS REs for the first symbol areexhausted.

When employing the time-first mapping of FIG. 22, the DM-RS sequence maybe firstly mapped on the DM-RS REs of the lowest subcarrier in a timeascending order (i.e. for the first symbol and then for the secondsymbol), and next, be mapped on the DM-RS REs of the second lowestsubcarrier in the time ascending order.

In an example, the above mechanism can be applied for the case whendistributed transmission is employed for the short NR PUCCH spanning 1or 2 symbols or frequency hopping may be applied for the transmission ofthe 2-symbol short NR PUCCH.

In addition, in order to support multiple user-multiple input multipleoutput (MU-MIMO), orthogonal cover code (OCC) may be used to enhance theDM-RS sequence design for the short NR PUCCH with more than 2 bits UCI.

In some embodiments, OCC may be applied to the DM-RS REs within 1 PRB(1-symbol duration) or within 2 PRBs (2-symbol duration) to support theorthogonal MU-MIMO.

FIG. 23 illustrates an example of applying OCC to the DM-RS REs within 1PRB (i.e. frequency domain OCC). In this example, OCC with length of 2bits may be used to define two orthogonal DM-RS sequences. For example,OCC=[1 1] and [1-1] may be used to support orthogonal MU-MIMO. Aftergenerating DM-RS sequences for two UEs (e.g. UE1 and UE2), [1 1] can beapplied to the DM-RS sequence for UE1 and [1-1] may be applied to theDM-RS sequence for UE2. As a result, for UE1, the DM-RS sequence on thefirst RE may be multiplied by 1 and the DM-RS sequence on the second REmay be multiplied by 1, and for UE2, the DM-RS sequence on the first REmay be multiplied by 1 and the DM-RS sequence on the second RE may bemultiplied by −1.

FIG. 24 illustrates an example of applying OCC to the DM-RS REs within 2PRBs (i.e. time domain OCC). In this example, frequency mapping with thesame sequence value in each symbol may be employed. For example, OCCwith length of 2 bits is applied to define two orthogonal DM-RSsequences. In one example, OCC=[1 1] and [1−1] may be used to supportorthogonal MU-MIMO. After generating DM-RS for two UEs (e.g. UE1 andUE2), [1 1] may be applied to DM-RS sequence for UE1 and [1−1] may beapplied to DM-RS sequence for UE2. For UE1, the DM-RS sequence on thefirst symbol may be multiplied by 1 and the DM-RS sequence on the secondsymbol may be multiplied by 1. For UE2, the DM-RS sequence on the firstsymbol may be multiplied by 1 and the DM-RS sequence on the secondsymbol may be multiplied by −1. It is to be noted that the frequencydomain OCC may also be applicable in this case. Moreover, said OCC mayhave any suitable length.

In addition, when applying the OCC to the DM-RS sequence in frequencydomain or in time domain, the initialization seed for the generation ofDM-RS sequence may be defined with same scrambling ID and without theUE-specific parameter (e.g., UE ID or C-RNTI), in order to supportorthogonal MU-MIMO.

In an example, at least some of the UEs transmitting at the sameposition may use the same UE ID or the same scrambling ID. In otherword, the DM-RS sequences for the UEs are the same, and the OCC may beused to distinguish these UEs.

Note that the OCC used for transmission of DM-RS sequence on the shortNR PUCCH may be configured by higher layers via UE specific RRCsignaling, or dynamically indicated in the DCI or a combination thereof.Alternatively, it may be determined for different UCI type. Forinstance, for short PUCCH carrying HARQ-ACK feedback, OCC used for thetransmission of DM-RS sequences may be dynamically indicated in the DCI,while for short PUCCH carrying CSI report, OCC used for the transmissionof DM-RS sequences may be configured by higher layers via RRC signaling.

In accordance with some embodiments, a machine readable medium may storeinstructions associated with any example of the method 2000 that, whenexecuted, may cause a UE to perform the steps of any example of themethod 2000.

In accordance with some embodiments, an apparatus may comprise variousfunction modules for performing the steps of any example for the method2000.

In some embodiments, the electronic device(s), network(s), system(s),chip(s) or component(s), or portions or implementations thereof, of FIG.2, FIG. 3 or other figures herein may be configured to perform one ormore processes, techniques, or methods as described herein, or portionsthereof.

It should be noted that, some embodiments of the present disclosure arediscussed in the context of 5G network and New Radio (NR). However,persons skilled in the art would understand that these embodimentspossibly are applicable to other networks such as LTE, LTE-Advanced, oreven applicable to coexistence of LTE, LTE-Advanced and NR.

Some non-limiting examples are provided below. The examples herein mayinclude subject matters such as apparatus, user device, method, meansfor performing the steps of a method, machine-readable medium includinginstructions that, when executed by a machine such as a processor withmemory, an application-specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or the like, cause the machine to performthe steps of the method, network node and communication system.

EXAMPLES

Example 1 is an apparatus for a user equipment (UE), comprising: aninterface configured to enable the UE to communicate with two or moretransmission reception points (TRPs); and a processor that is configuredto generate uplink control information (UCI) for each of the TRPs,schedule single or multiple uplink channels to carry the UCI, so thatthe UCI is transmitted individually or in combination to the TRPs viathe interface, wherein the uplink channels comprise new radio (NR)physical uplink control channel (PUCCH) and/or NR physical uplink sharedchannel (PUSCH).

Example 2 may comprise the subject matter of Example 1, wherein said UCIcomprises hybrid automatic repeat request (HARQ)acknowledgement/negative acknowledgement (ACK/NACK) feedback and/orchannel state information (CSI) report.

Example 3 may comprise the subject matter of Example 1 or 2, wherein theprocessor is further configured to schedule the multiple uplink channelseach carrying the UCI generated for one of the TRPs, wherein themultiple uplink channels are multiplexed in a time division multiplexing(TDM) manner, or in a frequency division multiplexing (FDM) manner.

Example 4 may comprise the subject matter of Example 3, wherein theprocessor is further configured to schedule the multiple uplink channelsaccording to resource allocation in time domain or in frequency domain,which is configured by higher layers and/or dynamically configured bydownlink control information (DCI) from the TRPs.

Example 5 may comprise the subject matter of Example 4, whereininformation regarding the resource allocation in time domain isexchanged between the TRPs in a semi-static or dynamic manner; orwherein the resource allocation in frequency domain is contiguous, basedon semi-static or dynamic coordination between the TRPs.

Example 6 may comprise the subject matter of Example 3, wherein theprocessor is further configured to select one of the multiple uplinkchannels for transmission and drop the others, when the UE supports onlyone transmit (Tx) beam or antenna port, in case of the FDM manner.

Example 7 may comprise the subject matter of Example 6, wherein thedropping is based on a dropping rule or priority rule, which ispredefined in 3GPP specification or configured by higher layers; orwherein the dropping is based on channel quality of the uplink channels.

Example 8 may comprise the subject matter of Example 1, wherein theprocessor is further configured to: combine the UCI generated for eachof the TRPs into a bit set, wherein each UCI corresponds to a subset ofsaid bit set; and schedule the single uplink channel to carry said bitset, wherein said bit set is to be transmitted to one of the TRPs whichis to forward said bit set to the remaining TRPs, or wherein said bitset is to be transmitted simultaneously to each of the TRPs if the UEsupports multiple transmit (Tx) beams.

Example 9 may comprise the subject matter of Example 1, wherein theprocessor is further configured to: combine the UCI generated for eachof the TRPs into a bit set, wherein each UCI corresponds to a subset ofsaid bit set; and schedule the multiple uplink channels each carryingsaid bit set, wherein said bit set is to be transmitted simultaneouslyto each of the TRPs if the UE supports multiple transmit (Tx) beams, orwherein said bit set is to be transmitted to each of the TRPs by meansof beam sweeping if the UE only supports single Tx beam.

Example 10 may comprise the subject matter of Example 8 or 9, whereinTRP index for said bit set is predefined in 3GPP specification orconfigured by higher layers, or wherein said bit set only includes theUCI generated for the TRPs for the corresponding HARQ-ACK feedback.

Example 11 may comprise the subject matter of Example 8 or 9, wherein anumber of bits in each subset is configured by higher layers and/orindicated by downlink control information (DCI) from the TRPs.

Example 12 may comprise the subject matter of Example 8 or 9, wherein incase of scheduling a PUCCH to carry said bit set, the processor isfurther configured to dynamically select a format of the PUCCH based ondownlink control information (DCI) from the TRPs, according to a numberof bits in said bit set.

Example 13 is a machine readable medium comprising instructions that,when executed, cause a user equipment (UE) to generate uplink controlinformation (UCI) for each of two or more transmission reception points(TRPs) communicating with the UE, and schedule single or multiple uplinkchannels to carry the UCI, so that the UCI is transmitted individuallyor in combination to the TRPs via the interface, wherein the uplinkchannels comprise new radio (NR) physical uplink control channel (PUCCH)and/or NR physical uplink shared channel (PUSCH).

Example 14 may comprise the subject matter of Example 13, wherein saidUCI comprises hybrid automatic repeat request (HARQ)acknowledgement/negative acknowledgement (ACK/NACK) feedback and/orchannel state information (CSI) report.

Example 15 may comprise the subject matter of Example 13 or 14, whereinthe instructions, when executed, further cause the UE to schedule themultiple uplink channels each carrying the UCI generated for one of theTRPs, wherein the multiple uplink channels are multiplexed in a timedivision multiplexing (TDM) manner, or in a frequency divisionmultiplexing (FDM) manner.

Example 16 may comprise the subject matter of Example 15, wherein theinstructions, when executed, further cause the UE to schedule themultiple uplink channels according to resource allocation in time domainor in frequency domain, which is configured by higher layers and/ordynamically configured by downlink control information (DCI) from theTRPs.

Example 17 may comprise the subject matter of Example 16, whereininformation regarding the resource allocation in time domain isexchanged between the TRPs in a semi-static or dynamic manner; orwherein the resource allocation in frequency domain is contiguous, basedon semi-static or dynamic coordination between the TRPs.

Example 18 may comprise the subject matter of Example 15, wherein theinstructions, when executed, further cause the UE to select one of themultiple uplink channels for transmission and drop the others, when theUE supports only one transmit (Tx) beam or antenna port, in case of theFDM manner.

Example 19 may comprise the subject matter of Example 18, wherein thedropping is based on a dropping rule or priority rule, which ispredefined in 3GPP specification or configured by higher layers; orwherein the dropping is based on channel quality of the uplink channels.

Example 20 may comprise the subject matter of Example 13, wherein theinstructions, when executed, further cause the UE to combine the UCIgenerated for each of the TRPs into a bit set, wherein each UCIcorresponds to a subset of said bit set, and schedule the single uplinkchannel to carry said bit set, wherein said bit set is to be transmittedto one of the TRPs which is to forward said bit set to the remainingTRPs, or wherein said bit set is to be transmitted simultaneously toeach of the TRPs if the UE supports multiple transmit (Tx) beams.

Example 21 may comprise the subject matter of Example 13, wherein theinstructions, when executed, further cause the UE to: combine the UCIgenerated for each of the TRPs into a bit set, wherein each UCIcorresponds to a subset of said bit set; and schedule the multipleuplink channels each carrying said bit set, wherein said bit set is tobe transmitted simultaneously to each of the TRPs if the UE supportsmultiple transmit (Tx) beams, or wherein said bit set is to betransmitted to each of the TRPs by means of beam sweeping if the UE onlysupports single Tx beam.

Example 22 may comprise the subject matter of Example 20 or 21, whereinTRP index for said bit set is predefined in 3GPP specification orconfigured by higher layers, or wherein said bit set only includes theUCI generated for the TRPs for the corresponding HARQ-ACK feedback.

Example 23 may comprise the subject matter of Example 20 or 21, whereina number of bits in each subset is configured by higher layers and/orindicated by downlink control information (DCI) from the TRPs.

Example 24 may comprise the subject matter of Example 20 or 21, whereinthe instructions, when executed, further cause the UE to dynamicallyselect a format of the PUCCH based on downlink control information (DCI)from the TRPs, according to a number of bits in said bit set, in case ofscheduling a PUCCH to carry said bit set.

Example 25 is an apparatus for a network node having two or moretransmission reception points (TRPs), comprising a processor configuredto: enable the two or more TRPs to communicate with a UE and to receivea bit set via single or multiple uplink channels, said bit set includingmultiple subsets each corresponding to uplink control information (UCI)for one of the TRPs; coordinate between the two or more TRPs; andgenerate downlink control information (DCI) for the UE, wherein theuplink channels comprise new radio (NR) physical uplink control channel(PUCCH) and/or NR physical uplink shared channel (PUSCH).

Example 26 may comprise the subject matter of Example 25, wherein saidDCI comprises one or more of: information indicating resource allocationin time domain for the uplink channels; information indicating resourceallocation in frequency domain for the uplink channels; informationindicating a number of bits in each of the multiple subsets; andinformation indicating a format of the PUCCH carrying the bit set.

Example 27 is a user equipment (UE) comprising the subject matter ofExample 1 and a radio frequency (RF) circuitry.

Example 28 is a network node comprising the subject matter of Example 25or 26, and two or more transmission reception points (TRPs).

Example 29 is a network node comprising the subject matter of Example 25or 26, and a radio frequency (RF) circuitry.

Example 30 is a communication system comprising the subject matter ofExample 27 and the subject matter of Example 28 or 29.

Example 31 is a method employable at a UE to facilitate multi-TRPoperation, comprising the steps of: generating uplink controlinformation (UCI) for each of two or more TRPs communicating with theUE; and scheduling single or multiple uplink channels to carry the UCI,so that the UCI may be transmitted over the scheduled uplink channelsindividually or in combination to the TRPs, via an interface, whereinthe uplink channels may comprise NR PUCCH and/or NR PUSCH.

Example 32 may comprise the subject matter of Example 31, and one ormore additional steps or operations as discussed in the disclosure.

Example 33 is an apparatus comprising various means or functionalmodules for performing the steps of the method of Example 31 or 32.

Example 34 is a method employable at a network node to facilitatemulti-TRP operation, comprising the steps of: enabling two or more TRPsin the network node to communicate with a UE and to receive a bit setvia single or multiple uplink channels, said bit set including multiplesubsets each corresponding to uplink control information (UCI) for oneof the TRPs; coordinating between the two or more TRPs; and generatingdownlink control information (DCI) for the UE, wherein the uplinkchannels comprise NR PUCCH and/or NR PUSCH.

Example 35 may comprise the subject matter of Example 34, and one ormore additional steps or operations as discussed in the disclosure.

Example 36 is an apparatus comprising various means or functionalmodules for performing the steps of the method of Example 34 or 35.

Example 37 is an apparatus for a user equipment (UE) operable tocommunicate with a new radio (NR) network node, comprising a processorconfigured to: generate a pseudo noise (PN) sequence based on aninitialization seed; generate a demodulation reference signal (DM-RS)sequence based on the PN sequence; and map the DM-RS sequence onphysical resource allocated for transmission of a short physical uplinkcontrol channel (PUCCH) with more than 2 bits uplink control information(UCI).

Example 38 may comprise the subject matter of Example 37, wherein theprocessor is further configured to define said initialization seed as afunction of one or more of the following parameters: slot index ormini-slot index for transmission of the short PUCCH; symbol index orstarting symbol index for transmission of the short PUCCH; scramblingidentity (ID), or physical cell ID when the scrambling ID is notavailable; beam ID; and UE-specific parameter.

Example 39 may comprise the subject matter of Example 38, wherein theUE-specific parameter comprises a bandwidth part (BWP) ID, an offsetparameter, or a UE ID including a cell radio network temporaryidentifier (C-RNTI) of the UE.

Example 40 may comprise the subject matter of Example 38 or 39, whereinthe scrambling ID is configured by higher layers via NR minimum systeminformation (MSI), NR remaining minimum system information (RMSI), NRother system information (OSI) or radio resource control (RRC)signaling, and/or is dynamically indicated by downlink controlinformation (DCI) from the network node.

Example 41 may comprise the subject matter of Example 38 or 39, whereinthe scrambling ID is configured independently for different bandwidthparts (BWPs) being active within a system bandwidth, and/or fordifferent types of the UCI.

Example 42 may comprise the subject matter of Example 38 or 39, whereinin case of the short PUCCH spanning two symbols, the initialization seedis defined independently for each symbol as a function of its respectivesymbol index.

Example 43 may comprise the subject matter of Example 41, wherein theUCI carried by the short PUCCH is a hybrid automatic repeat request(HARQ) acknowledgement/negative acknowledgement (ACK/NACK) feedback fora corresponding physical downlink shared channel (PDSCH) from thenetwork node, and wherein the scrambling ID used for the DM-RS sequenceon the short PUCCH is the same as that for the DM-RS sequence on thePDSCH, or is dynamically switched according to downlink controlinformation (DCI) from the network node.

Example 44 may comprise the subject matter of Example 38 or 39, whereinthe scrambling ID is configured based on an index of a set of {P0,alpha} for uplink power control and/or pathloss.

Example 45 may comprise the subject matter of Example 37, wherein theprocessor is further configured to: generate same PN sequence for theDM-RS sequence on the short PUCCH and on a PUSCH with cyclicprefix-orthogonal frequency division multiplexing (CP-OFDM) basedwaveform.

Example 46 may comprise the subject matter of Example 37, 38 or 39,wherein the processor is adapted to generate the DM-RS sequenceaccording to at least a maximum number of physical resource blocks(PRBs) supported for a given subcarrier spacing within a widebandcomponent carrier (CC), and map the DM-RS sequence on said physicalresource using a common PRB indexing with regard to the wideband CC. Inan alternative example, the processor is adapted to generate the DM-RSsequence according to at least a total number of PRBs supported for agiven subcarrier spacing within a configured bandwidth part (BWP), andmap the DM-RS sequence on said physical resource using a UE-specific PRBindexing for the given subcarrier spacing within the configured BWP. Inan alternative example, the processor is adapted to generate the DM-RSsequence according to at least a number of PRBs allocated in frequencydomain for transmission of the short PUCCH, and map the DM-RS sequenceon the allocated PRBs.

Example 47 may comprise the subject matter of Example 46, wherein theDM-RS sequence is generated according to also a number of symbolsallocated in time domain for transmission of the short PUCCH.

Example 48 may comprise the subject matter of Example 47, wherein theprocessor is further configured to select one of a time-first mappingmanner and a frequency-first mapping manner to map the DM-RS sequence onsaid physical resource, in case of the short PUCCH spanning two symbols.

Example 49 may comprise the subject matter of Example 47, wherein theprocessor is further configured to employing a time-first mapping manneror a frequency-first mapping manner which is configured by higher layersvia NR minimum system information (MSI), NR remaining minimum systeminformation (RMSI), NR other system information (OSI) or radio resourcecontrol (RRC) signaling.

Example 50 may comprise the subject matter of Example 38 or 39, whereinthe processor is further configured to apply an orthogonal cover code(OCC) to the DM-RS sequence in frequency domain or in time domain, whenthe initialization seed is defined with same scrambling ID and withoutsaid UE-specific parameter.

Example 51 may comprise the subject matter of Example 50, wherein theOCC is configured by higher layers or dynamically indicated in downlinkcontrol information (DCI) or a combination thereof.

Example 52 is a machine readable medium comprising instructions that,when executed, cause a user equipment (UE) operable to communicate witha new radio (NR) network node to: generate a pseudo noise (PN) sequencebased on an initialization seed; generate a demodulation referencesignal (DM-RS) sequence based on the PN sequence; and map the DM-RSsequence on physical resource allocated for transmission of a shortphysical uplink control channel (PUCCH) with more than 2 bits uplinkcontrol information (UCI).

Example 53 may comprise the subject matter of Example 52, wherein theinstructions, when executed, further cause the UE to define saidinitialization seed as a function of one or more of the followingparameters: slot index or mini-slot index for transmission of the shortPUCCH; symbol index or starting symbol index for transmission of theshort PUCCH; scrambling identity (ID), or physical cell ID when thescrambling ID is not available; beam ID; and UE-specific parameter.

Example 54 may comprise the subject matter of Example 53, wherein theUE-specific parameter comprises a bandwidth part (BWP) ID, an offsetparameter, or a UE ID including a cell radio network temporaryidentifier (C-RNTI) of the UE.

Example 55 may comprise the subject matter of Example 53 or 54, whereinthe scrambling ID is configured by higher layers via NR minimum systeminformation (MSI), NR remaining minimum system information (RMSI), NRother system information (OSI) or radio resource control (RRC)signaling, and/or is dynamically indicated by downlink controlinformation (DCI) from the network node.

Example 56 may comprise the subject matter of Example 53 or 54, whereinthe scrambling ID is configured independently for different bandwidthparts (BWPs) being active within a system bandwidth, and/or fordifferent types of the UCI.

Example 57 may comprise the subject matter of Example 53 or 54, whereinin case of the short PUCCH spanning two symbols, the initialization seedis defined independently for each symbol as a function of its respectivesymbol index.

Example 58 may comprise the subject matter of Example 56, wherein theUCI carried by the short PUCCH is a hybrid automatic repeat request(HARQ) acknowledgement/negative acknowledgement (ACK/NACK) feedback fora corresponding physical downlink shared channel (PDSCH) from thenetwork node; and wherein the scrambling ID used for the DM-RS sequenceon the short PUCCH is the same as that for the DM-RS sequence on thePDSCH, or is dynamically switched according to downlink controlinformation (DCI) from the network node.

Example 59 may comprise the subject matter of Example 53 or 54, whereinthe scrambling ID is configured based on an index of a set of {P0,alpha} for uplink power control and/or pathloss.

Example 60 may comprise the subject matter of Example 52, wherein theinstructions, when executed, further cause the UE to generate same PNsequence for the DM-RS sequence on the short PUCCH and on a PUSCH withcyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) basedwaveform.

Example 61 may comprise the subject matter of Example 52, 53 or 54,wherein the instructions, when executed, further cause the UE togenerate the DM-RS sequence according to at least a maximum number ofphysical resource blocks (PRBs) supported for a given subcarrier spacingwithin a wideband component carrier (CC), and map the DM-RS sequence onsaid physical resource using a common PRB indexing with regard to thewideband CC. In an alternative example, the instructions, when executed,further cause the UE to generate the DM-RS sequence according to atleast a total number of PRBs supported for a given subcarrier spacingwithin a configured bandwidth part (BWP), and map the DM-RS sequence onsaid physical resource using a UE-specific PRB indexing for the givensubcarrier spacing within the configured BWP. In an alternative example,the instructions, when executed, further cause the UE to generate theDM-RS sequence according to at least a number of PRBs allocated infrequency domain for transmission of the short PUCCH, and map the DM-RSsequence on the allocated PRBs.

Example 62 may comprise the subject matter of Example 61, wherein theDM-RS sequence is generated according to also a number of symbolsallocated in time domain for transmission of the short PUCCH.

Example 63 may comprise the subject matter of Example 62, wherein theinstructions, when executed, further cause the UE to select one of atime-first mapping manner and a frequency-first mapping manner to mapthe DM-RS sequence on said physical resource, in case of the short PUCCHspanning two symbols.

Example 64 may comprise the subject matter of Example 62, wherein theinstructions, when executed, further cause the UE to employing atime-first mapping manner or a frequency-first mapping manner which isconfigured by higher layers via NR minimum system information (MSI), NRremaining minimum system information (RMSI), NR other system information(OSI) or radio resource control (RRC) signaling.

Example 65 may comprise the subject matter of Example 53 or 54, whereinthe instructions, when executed, further cause the UE to apply anorthogonal cover code (OCC) to the DM-RS sequence in frequency domain orin time domain, when the initialization seed is defined with samescrambling ID and without said UE-specific parameter.

Example 66 may comprise the subject matter of Example 65, wherein theOCC is configured by higher layers or dynamically indicated in downlinkcontrol information (DCI) or a combination thereof.

Example 67 is a user equipment (UE) comprising the subject matter ofExample 37 and a radio frequency (RF) circuitry.

Example 68 is a network node adapted to receive the short NR PUCCH fromthe UE of Example 67 and use the DM-RS derived from the short NR PUCCHfor channel estimation and demodulation.

Example 69 is a communication system comprising the subject matter ofExample 67 and the subject matter of Example 68.

Example 70 is a method employable at a UE, comprising the steps ofgenerating a pseudo noise (PN) sequence based on an initialization seed;generating a demodulation reference signal (DM-RS) sequence based on thePN sequence; and mapping the DM-RS sequence on physical resourceallocated for transmission of a short PUCCH with more than 2 bits UCI.

Example 71 may comprise the subject matter of Example 70, and one ormore additional steps or operations as discussed in the disclosure.

Example 72 is an apparatus comprising various means or functionalmodules for performing the steps of the method of Example 70 or 71.

Example 73 is a method employable at a network node of Example 68,comprising the steps of receiving the short NR PUCCH from the UE ofExample 67, and using the DM-RS derived from the short NR PUCCH forchannel estimation and demodulation.

Example 74 is an apparatus comprising various means or functionalmodules for performing the steps of the method of Example 73.

Example 75 may include a signal as described in relation to any ofExamples 1 to 74.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as recognized by those skilled in the relevant art.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

In particular regard to the various functions performed by the abovedescribed components or structures (assemblies, devices, circuits,systems, etc.), the terms (including a reference to a “means”) used todescribe such components are intended to correspond, unless otherwiseindicated, to any component or structure which performs the specifiedfunction of the described component (e.g., that is functionallyequivalent), even though not structurally equivalent to the disclosedstructure which performs the function in the herein illustratedexemplary implementations. In addition, while a particular feature mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application.

1-46. (canceled)
 47. An apparatus for a user equipment (UE), comprising:an interface configured to enable the UE to communicate with two or moretransmission reception points (TRPs); and a processor configured to:generate uplink control information (UCI) for each of the TRPs, schedulesingle or multiple uplink channels to carry the UCI, so that the UCI istransmitted individually or in combination to the TRPs via theinterface, wherein the uplink channels comprise new radio (NR) physicaluplink control channel (PUCCH) and/or NR physical uplink shared channel(PUSCH).
 48. The apparatus of claim 47, wherein said UCI compriseshybrid automatic repeat request (HARQ) acknowledgement/negativeacknowledgement (ACK/NACK) feedback and/or channel state information(CSI) report.
 49. The apparatus of claim 47, wherein the processor isfurther configured to: schedule the multiple uplink channels eachcarrying the UCI generated for one of the TRPs, wherein the multipleuplink channels are multiplexed in a time division multiplexing (TDM)manner, or in a frequency division multiplexing (FDM) manner.
 50. Theapparatus of claim 49, wherein the processor is further configured to:schedule the multiple uplink channels according to resource allocationin time domain or in frequency domain, which is configured by higherlayers and/or dynamically configured by downlink control information(DCI) from the TRPs.
 51. The apparatus of claim 49, wherein theprocessor is further configured to: select one of the multiple uplinkchannels for transmission and drop the others, when the UE supports onlyone transmit (Tx) beam or antenna port, in case of the FDM manner. 52.The apparatus of claim 47, wherein the processor is further configuredto: combine the UCI generated for each of the TRPs into a bit set,wherein each UCI corresponds to a subset of said bit set; and schedulethe single uplink channel to carry said bit set, wherein said bit set isto be transmitted to one of the TRPs which is to forward said bit set tothe remaining TRPs, or wherein said bit set is to be transmittedsimultaneously to each of the TRPs if the UE supports multiple transmit(Tx) beams.
 53. The apparatus of claim 47, wherein the processor isfurther configured to: combine the UCI generated for each of the TRPsinto a bit set, wherein each UCI corresponds to a subset of said bitset; and schedule the multiple uplink channels each carrying said bitset, wherein said bit set is to be transmitted simultaneously to each ofthe TRPs if the UE supports multiple transmit (Tx) beams, or whereinsaid bit set is to be transmitted to each of the TRPs by means of beamsweeping if the UE only supports single Tx beam.
 54. The apparatus ofclaim 52, wherein TRP index for said bit set is predefined in 3G PPspecification or configured by higher layers, or wherein said bit setonly includes the UCI generated for the TRPs for the correspondingHARQ-ACK feedback.
 55. The apparatus of claim 52, wherein a number ofbits in each subset is configured by higher layers and/or indicated bydownlink control information (DCI) from the TRPs.
 56. The apparatus ofclaim 52, wherein in case of scheduling a PUCCH to carry said bit set,the processor is further configured to: dynamically select a format ofthe PUCCH based on downlink control information (DCI) from the TRPs,according to a number of bits in said bit set.
 57. A machine readablemedium comprising instructions that, when executed, cause a userequipment (UE) to: generate uplink control information (UCI) for each oftwo or more transmission reception points (TRPs) communicating with theUE, schedule single or multiple uplink channels to carry the UCI, sothat the UCI is transmitted individually or in combination to the TRPsvia the interface, wherein the uplink channels comprise new radio (NR)physical uplink control channel (PUCCH) and/or NR physical uplink sharedchannel (PUSCH).
 58. The machine readable medium of claim 57, whereinsaid UCI comprises hybrid automatic repeat request (HARQ)acknowledgement/negative acknowledgement (ACK/NACK) feedback and/orchannel state information (CSI) report.
 59. The machine readable mediumof claim 57, wherein the instructions, when executed, further cause theUE to: schedule the multiple uplink channels each carrying the UCIgenerated for one of the TRPs, wherein the multiple uplink channels aremultiplexed in a time division multiplexing (TDM) manner, or in afrequency division multiplexing (FDM) manner.
 60. The machine readablemedium of claim 59, wherein the instructions, when executed, furthercause the UE to: schedule the multiple uplink channels according toresource allocation in time domain or in frequency domain, which isconfigured by higher layers and/or dynamically configured by downlinkcontrol information (DCI) from the TRPs.
 61. The machine readable mediumof claim 59, wherein the instructions, when executed, further cause theUE to: select one of the multiple uplink channels for transmission anddrop the others, when the UE supports only one transmit (Tx) beam orantenna port, in case of the FDM manner.
 62. The machine readable mediumof claim 57, wherein the instructions, when executed, further cause theUE to: combine the UCI generated for each of the TRPs into a bit set,wherein each UCI corresponds to a subset of said bit set; and schedulethe single uplink channel to carry said bit set, wherein said bit set isto be transmitted to one of the TRPs which is to forward said bit set tothe remaining TRPs, or wherein said bit set is to be transmittedsimultaneously to each of the TRPs if the UE supports multiple transmit(Tx) beams.
 63. The machine readable medium of claim 57, wherein theinstructions, when executed, further cause the UE to: combine the UCIgenerated for each of the TRPs into a bit set, wherein each UCIcorresponds to a subset of said bit set; and schedule the multipleuplink channels each carrying said bit set, wherein said bit set is tobe transmitted simultaneously to each of the TRPs if the UE supportsmultiple transmit (Tx) beams, or wherein said bit set is to betransmitted to each of the TRPs by means of beam sweeping if the UE onlysupports single Tx beam.
 64. The machine readable medium of claim 62,wherein TRP index for said bit set is predefined in 3GPP specificationor configured by higher layers, or wherein said bit set only includesthe UCI generated for the TRPs for the corresponding HARQ-ACK feedback.65. The machine readable medium of claim 62, wherein a number of bits ineach subset is configured by higher layers and/or indicated by downlinkcontrol information (DCI) from the TRPs.
 66. The machine readable mediumof claim 62, wherein the instructions, when executed, further cause theUE to: dynamically select a format of the PUCCH based on downlinkcontrol information (DCI) from the TRPs, according to a number of bitsin said bit set, in case of scheduling a PUCCH to carry said bit set.67. An apparatus for a user equipment (UE) operable to communicate witha new radio (NR) network node, comprising: a processor configured to:generate a pseudo noise (PN) sequence based on an initialization seed;generate a demodulation reference signal (DM-RS) sequence based on thePN sequence; and map the DM-RS sequence on physical resource allocatedfor transmission of a short physical uplink control channel (PUCCH) withmore than 2 bits uplink control information (UCI).
 68. The apparatus ofclaim 67, wherein the processor is further configured to define saidinitialization seed as a function of one or more of the followingparameters: slot index or mini-slot index for transmission of the shortPUCCH; symbol index or starting symbol index for transmission of theshort PUCCH; scrambling identity (ID), or physical cell ID when thescrambling ID is not available; beam ID; and UE-specific parameter. 69.The apparatus of claim 68, wherein the UE-specific parameter comprises abandwidth part (BWP) ID, an offset parameter, or a UE ID including acell radio network temporary identifier (C-RNTI) of the UE.
 70. Theapparatus of claim 68, wherein the scrambling ID is configured by higherlayers via NR minimum system information (MSI), NR remaining minimumsystem information (RMSI), NR other system information (OSI) or radioresource control (RRC) signaling, and/or is dynamically indicated bydownlink control information (DCI) from the network node.
 71. Theapparatus of claim 68, wherein the scrambling ID is configuredindependently for different bandwidth parts (BWPs) being active within asystem bandwidth, and/or for different types of the UCI.
 72. Theapparatus of claim 68, wherein in case of the short PUCCH spanning twosymbols, the initialization seed is defined independently for eachsymbol as a function of its respective symbol index.
 73. The apparatusof claim 71, wherein the UCI carried by the short PUCCH is a hybridautomatic repeat request (HARQ) acknowledgement/negative acknowledgement(ACK/NACK) feedback for a corresponding physical downlink shared channel(PDSCH) from the network node; and wherein the scrambling ID used forthe DM-RS sequence on the short PUCCH is the same as that for the DM-RSsequence on the PDSCH, or is dynamically switched according to downlinkcontrol information (DCI) from the network node.
 74. The apparatus ofclaim 67, wherein the processor is adapted to: generate the DM-RSsequence according to at least a maximum number of physical resourceblocks (PRBs) supported for a given subcarrier spacing within a widebandcomponent carrier (CC), and map the DM-RS sequence on said physicalresource using a common PRB indexing with regard to the wideband CC. 75.The apparatus of claim 67, wherein the processor is adapted to generatethe DM-RS sequence according to at least a total number of PRBssupported for a given subcarrier spacing within a configured bandwidthpart (BWP), and map the DM-RS sequence on said physical resource using aUE-specific PRB indexing for the given subcarrier spacing within theconfigured BWP.
 76. The apparatus of claim 67, wherein the processor isadapted to generate the DM-RS sequence according to at least a number ofPRBs allocated in frequency domain for transmission of the short PUCCH,and map the DM-RS sequence on the allocated PRBs.
 77. The apparatus ofclaim 74, wherein the DM-RS sequence is generated according to also anumber of symbols allocated in time domain for transmission of the shortPUCCH.
 78. The apparatus of claim 77, wherein the processor is furtherconfigured to: employ a frequency-first mapping manner to map the DM-RSsequence on said physical resource, in case of the short PUCCH spanningtwo symbols.
 79. The apparatus of claim 68, wherein the processor isfurther configured to: apply an orthogonal cover code (OCC) to the DM-RSsequence in frequency domain or in time domain, when the initializationseed is defined with same scrambling ID and without said UE-specificparameter.
 80. A machine readable medium comprising instructions that,when executed, cause a user equipment (UE) operable to communicate witha new radio (NR) network node to: generate a pseudo noise (PN) sequencebased on an initialization seed; generate a demodulation referencesignal (DM-RS) sequence based on the PN sequence; and map the DM-RSsequence on physical resource allocated for transmission of a shortphysical uplink control channel (PUCCH) with more than 2 bits uplinkcontrol information (UCI).
 81. The machine readable medium of claim 80,wherein the instructions, when executed, further cause the UE to definesaid initialization seed as a function of one or more of the followingparameters: slot index or mini-slot index for transmission of the shortPUCCH; symbol index or starting symbol index for transmission of theshort PUCCH; scrambling identity (ID), or physical cell ID when thescrambling ID is not available; beam ID; and UE-specific parameter. 82.The machine readable medium of claim 81, wherein the UE-specificparameter comprises a bandwidth part (BWP) ID, an offset parameter, or aUE ID including a cell radio network temporary identifier (C-RNTI) ofthe UE.
 83. The machine readable medium of claim 81, wherein thescrambling ID is configured by higher layers via NR minimum systeminformation (MSI), NR remaining minimum system information (RMSI), NRother system information (OSI) or radio resource control (RRC)signaling, and/or is dynamically indicated by downlink controlinformation (DCI) from the network node.
 84. The machine readable mediumof claim 81, wherein the scrambling ID is configured independently fordifferent bandwidth parts (BWPs) being active within a system bandwidth,and/or for different types of the UCI.
 85. The machine readable mediumof claim 81, wherein in case of the short PUCCH spanning two symbols,the initialization seed is defined independently for each symbol as afunction of its respective symbol index.
 86. The machine readable mediumof claim 84, wherein the UCI carried by the short PUCCH is a hybridautomatic repeat request (HARQ) acknowledgement/negative acknowledgement(ACK/NACK) feedback for a corresponding physical downlink shared channel(PDSCH) from the network node; and wherein the scrambling ID used forthe DM-RS sequence on the short PUCCH is the same as that for the DM-RSsequence on the PDSCH or is dynamically switched according to downlinkcontrol information (DCI) from the network node.
 87. The machinereadable medium of claim 80, wherein the instructions, when executed,further cause the UE to: generate the DM-RS sequence according to atleast a maximum number of physical resource blocks (PRBs) supported fora given subcarrier spacing within a wideband component carrier (CC), andmap the DM-RS sequence on said physical resource using a common PRBindexing with regard to the wideband CC.
 88. The machine readable mediumof claim 80, wherein the instructions, when executed, further cause theUE to: generate the DM-RS sequence according to at least a total numberof PRBs supported for a given subcarrier spacing within a configuredbandwidth part (BWP), and map the DM-RS sequence on said physicalresource using a UE-specific PRB indexing for the given subcarrierspacing within the configured BWP.
 89. The machine readable medium ofclaim 80, wherein the instructions, when executed, further cause the UEto: generate the DM-RS sequence according to at least a number of PRBsallocated in frequency domain for transmission of the short PUCCH, andmap the DM-RS sequence on the allocated PRBs.
 90. The machine readablemedium of claim 87, wherein the DM-RS sequence is generated according toalso a number of symbols allocated in time domain for transmission ofthe short PUCCH.
 91. The machine readable medium of claim 90, whereinthe instructions, when executed, further cause the UE to: employ afrequency-first mapping manner to map the DM-RS sequence on saidphysical resource, in case of the short PUCCH spanning two symbols. 92.The machine readable medium of claim 81, wherein the instructions, whenexecuted, further cause the UE to: apply an orthogonal cover code (OCC)to the DM-RS sequence in frequency domain or in time domain, when theinitialization seed is defined with same scrambling ID and without saidUE-specific parameter.